SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Open Database Connectivity</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Open Database Connectivity</span></span>

</h1>

</header>

<p>In <a href="Computing" title="Computing">computing</a>, <b>Open Database Connectivity</b> (<b>ODBC</b>) is a standard <a href="Application_programming_interface" class="mw-redirect" title="Application programming interface">application programming interface</a> (API) for accessing <a href="Database_management_system" class="mw-redirect" title="Database management system">database management systems</a> (DBMS). The designers of ODBC aimed to make it independent of database systems and <a href="Operating_system" title="Operating system">operating systems</a>. An application written using ODBC can be <a href="Porting" title="Porting">ported</a> to other platforms, both on the client and server side, with few changes to the data access code.

</p><p>ODBC accomplishes DBMS independence by using an <i>ODBC <a href="Driver_(software)" title="Driver (software)">driver</a></i> as a translation layer between the application and the DBMS. The application uses ODBC functions through an <i>ODBC driver manager</i> with which it is linked, and the driver passes the <a href="Query_language" title="Query language">query</a> to the DBMS. An ODBC driver can be thought of as analogous to a printer driver or other driver, providing a standard set of functions for the application to use, and implementing DBMS-specific functionality. An application that can use ODBC is referred to as "ODBC-compliant". Any ODBC-compliant application can access any DBMS for which a driver is installed. Drivers exist for all major DBMSs, many other data sources like <a href="Address_book" title="Address book">address book</a> systems and <a href="Microsoft_Excel" title="Microsoft Excel">Microsoft Excel</a>, and even for text or <a href="Comma-separated_values" title="Comma-separated values">comma-separated values</a> (CSV) files.

</p><p>ODBC was originally developed by <a href="Microsoft" title="Microsoft">Microsoft</a> and <a href="Simba_Technologies" title="Simba Technologies">Simba Technologies</a> during the early 1990s, and became the basis for the <a href="Call_Level_Interface" title="Call Level Interface">Call Level Interface</a> (CLI) standardized by <a href="SQL_Access_Group" title="SQL Access Group">SQL Access Group</a> in the <a href="Unix" title="Unix">Unix</a> and <a href="Mainframe_computer" title="Mainframe computer">mainframe</a> field. ODBC retained several features that were removed as part of the CLI effort. Full ODBC was later ported back to those platforms, and became a <a href="De_facto_standard" title="De facto standard">de facto standard</a> considerably better known than CLI. The CLI remains similar to ODBC, and applications can be ported from one platform to the other with few changes.

</p>

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

<div class="mw-heading mw-heading3"><h3 id="Before_ODBC">Before ODBC</h3></div>

<p>The introduction of the <a href="Mainframe_computer" title="Mainframe computer">mainframe</a>-based <a href="Relational_database" title="Relational database">relational database</a> during the 1970s led to a proliferation of data access methods. Generally these systems operated together with a simple command processor that allowed users to type in English-like commands, and receive output. The best-known examples are <a href="SQL" title="SQL">SQL</a> from <a href="IBM" title="IBM">IBM</a> and <a href="QUEL_query_languages" title="QUEL query languages">QUEL</a> from the <a href="Ingres_(database)" title="Ingres (database)">Ingres</a> project. These systems may or may not allow other applications to access the data directly, and those that did use a wide variety of methodologies. The introduction of <a href="SQL" title="SQL">SQL</a> aimed to solve the problem of <i>language</i> standardization, although substantial differences in implementation remained.

</p><p>Since the SQL language had only rudimentary programming features, users often wanted to use SQL within a program written in another language, say <a href="Fortran" title="Fortran">Fortran</a> or <a href="C_(programming_language)" title="C (programming language)">C</a>. This led to the concept of <a href="Embedded_SQL" title="Embedded SQL">Embedded SQL</a>, which allowed <a href="PostQUEL" class="mw-redirect" title="PostQUEL">SQL</a> code to be <i>embedded</i> within another language. For instance, a SQL statement like <code>SELECT * FROM city</code> could be inserted as text within C source code, and during <a href="Compiler" title="Compiler">compiling</a> it would be converted into a custom format that directly called a function within a <a href="Library_(computing)" title="Library (computing)">library</a> that would pass the statement into the SQL system. Results returned from the statements would be interpreted back into C data formats like <code>char *</code> using similar library code.

</p><p>There were several problems with the Embedded SQL approach. Like the different varieties of SQL, the Embedded SQLs that used them varied widely, not only from platform to platform, but even across languages on one platform – a system that allowed calls into <a href="IBM_Db2" title="IBM Db2">IBM Db2</a> would look very different from one that called into their own <a href="IBM_SQL/DS" title="IBM SQL/DS">SQL/DS</a>. Another key problem to the Embedded SQL concept was that the SQL code could only be changed in the program's source code, so that even small changes to the query required considerable programmer effort to modify. The SQL market referred to this as <i>static SQL</i>, versus <i>dynamic SQL</i> which could be changed at any time, like the <a href="Command-line_interface" title="Command-line interface">command-line interfaces</a> that shipped with almost all SQL systems, or a programming interface that left the SQL as plain text until it was called. Dynamic SQL systems became a major focus for SQL vendors during the 1980s.

</p><p>Older mainframe databases, and the newer <a href="Microcomputer" title="Microcomputer">microcomputer</a> based systems that were based on them, generally did not have a SQL-like command processor between the user and the <a href="Database_engine" title="Database engine">database engine</a>. Instead, the data was accessed directly by the program – a programming library in the case of large mainframe systems, or a <a href="Command_line_interface" class="mw-redirect" title="Command line interface">command line interface</a> or interactive forms system in the case of <a href="DBASE" class="mw-redirect" title="DBASE">dBASE</a> and similar applications. Data from dBASE could not generally be accessed directly by other programs running on the machine. Those programs may be given a way to access this data, often through libraries, but it would not work with any other database engine, or even different databases in the same engine. In effect, all such systems were static, which presented considerable problems.

</p>

<div class="mw-heading mw-heading3"><h3 id="Early_efforts">Early efforts</h3></div>

<p>By the mid-1980s the rapid improvement in microcomputers, and especially the introduction of the <a href="Graphical_user_interface" title="Graphical user interface">graphical user interface</a> and data-rich <a href="Application_program" class="mw-redirect" title="Application program">application programs</a> like <a href="Lotus_1-2-3" title="Lotus 1-2-3">Lotus 1-2-3</a> led to an increasing interest in using personal computers as the client-side platform of choice in <a href="Client%E2%80%93server_model" title="Client–server model">client–server</a> computing. Under this model, large mainframes and <a href="Minicomputer" title="Minicomputer">minicomputers</a> would be used primarily to serve up data over <a href="Local_area_network" title="Local area network">local area networks</a> to microcomputers that would interpret, display and manipulate that data. For this model to work, a data access standard was a requirement – in the mainframe field it was highly likely that all of the computers in a shop were from one vendor and clients were <a href="Computer_terminal" title="Computer terminal">computer terminals</a> talking directly to them, but in the micro field there was no such standardization and any client might access any server using any networking system.

</p><p>By the late 1980s there were several efforts underway to provide an abstraction layer for this purpose. Some of these were mainframe related, designed to allow programs running on those machines to translate between the variety of SQL's and provide a single common interface which could then be called by other mainframe or microcomputer programs. These solutions included IBM's Distributed Relational Database Architecture (<a href="DRDA" title="DRDA">DRDA</a>) and <a href="Apple_Computer" class="mw-redirect" title="Apple Computer">Apple Computer</a>'s <a href="Data_Access_Language" title="Data Access Language">Data Access Language</a>. Much more common, however, were systems that ran entirely on microcomputers, including a complete <a href="Protocol_stack" title="Protocol stack">protocol stack</a> that included any required networking or file translation support.

</p><p>One of the early examples of such a system was <a href="Lotus_Development" class="mw-redirect" title="Lotus Development">Lotus Development</a>'s <a href="Lotus_DataLens" title="Lotus DataLens">DataLens</a>, initially known as Blueprint. Blueprint, developed for 1-2-3, supported a variety of data sources, including SQL/DS, DB2, <a href="FOCUS" title="FOCUS">FOCUS</a> and a variety of similar mainframe systems, as well as microcomputer systems like <a href="DBase" title="DBase">dBase</a> and the early Microsoft/Ashton-Tate efforts that would eventually develop into <a href="Microsoft_SQL_Server" title="Microsoft SQL Server">Microsoft SQL Server</a>.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> Unlike the later ODBC, Blueprint was a purely code-based system, lacking anything approximating a command language like SQL. Instead, programmers used <a href="Data_structure" title="Data structure">data structures</a> to store the query information, constructing a query by linking many of these structures together. Lotus referred to these compound structures as <i>query trees</i>.<sup id="cite_ref-FOOTNOTEGeiger199565_2-0" class="reference"><a href="#cite_note-FOOTNOTEGeiger199565-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>

</p><p>Around the same time, an industry team including members from <a href="Sybase" title="Sybase">Sybase</a> (Tom Haggin), <a href="Tandem_Computers" title="Tandem Computers">Tandem Computers</a> (<a href="Jim_Gray_(computer_scientist)" title="Jim Gray (computer scientist)">Jim Gray</a> & Rao Yendluri) and Microsoft (Kyle Geiger) were working on a standardized dynamic SQL concept. Much of the system was based on Sybase's DB-Library system, with the Sybase-specific sections removed and several additions to support other platforms.<sup id="cite_ref-FOOTNOTEGeiger199586-87_3-0" class="reference"><a href="#cite_note-FOOTNOTEGeiger199586-87-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> DB-Library was aided by an industry-wide move from library systems that were tightly linked to a specific language, to library systems that were provided by the <a href="Operating_system" title="Operating system">operating system</a> and required the languages on that platform to conform to its standards. This meant that a single library could be used with (potentially) any programming language on a given platform.

</p><p>The first draft of the <i>Microsoft Data Access API</i> was published in April 1989, about the same time as Lotus' announcement of Blueprint.<sup id="cite_ref-FOOTNOTEGeiger199556_4-0" class="reference"><a href="#cite_note-FOOTNOTEGeiger199556-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> In spite of Blueprint's great lead – it was running when MSDA was still a paper project – Lotus eventually joined the MSDA efforts as it became clear that SQL would become the de facto database standard.<sup id="cite_ref-FOOTNOTEGeiger199565_2-1" class="reference"><a href="#cite_note-FOOTNOTEGeiger199565-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> After considerable industry input, in the summer of 1989 the standard became <i>SQL Connectivity</i> (<i>SQLC</i>).<sup id="cite_ref-FOOTNOTEGeiger1995106_5-0" class="reference"><a href="#cite_note-FOOTNOTEGeiger1995106-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>

</p>

<p>In 1988 several vendors, mostly from the <a href="Unix" title="Unix">Unix</a> and database communities, formed the <a href="SQL_Access_Group" title="SQL Access Group">SQL Access Group</a> (SAG) in an effort to produce a single basic standard for the SQL language. At the first meeting there was considerable debate over whether or not the effort should work solely on the SQL language itself, or attempt a wider standardization which included a dynamic SQL language-embedding system as well, what they called a <a href="Call_Level_Interface" title="Call Level Interface">Call Level Interface</a> (CLI).<sup id="cite_ref-FOOTNOTEGeiger1995165_6-0" class="reference"><a href="#cite_note-FOOTNOTEGeiger1995165-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup> While attending the meeting with an early draft of what was then still known as MS Data Access, Kyle Geiger of Microsoft invited Jeff Balboni and Larry Barnes of <a href="Digital_Equipment_Corporation" title="Digital Equipment Corporation">Digital Equipment Corporation</a> (DEC) to join the SQLC meetings as well. SQLC was a potential solution to the call for the CLI, which was being led by DEC.

</p><p>The new SQLC "gang of four", MS, Tandem, DEC and Sybase, brought an updated version of SQLC to the next SAG meeting in June 1990.<sup id="cite_ref-FOOTNOTEGeiger1995186-187_7-0" class="reference"><a href="#cite_note-FOOTNOTEGeiger1995186-187-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> The SAG responded by opening the standard effort to any competing design, but of the many proposals, only <a href="Oracle_Corp" class="mw-redirect" title="Oracle Corp">Oracle Corp</a> had a system that presented serious competition. In the end, SQLC won the votes and became the draft standard, but only after large portions of the API were removed – the standards document was trimmed from 120 pages to 50 during this time. It was also during this period that the name Call Level Interface was formally adopted.<sup id="cite_ref-FOOTNOTEGeiger1995186-187_7-1" class="reference"><a href="#cite_note-FOOTNOTEGeiger1995186-187-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> In 1995 SQL/CLI became part of the international SQL standard, ISO/IEC 9075-3.<sup id="cite_ref-ISO/IEC_9075-3_8-0" class="reference"><a href="#cite_note-ISO/IEC_9075-3-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> The SAG itself was taken over by the <a href="X/Open" title="X/Open">X/Open</a> group in 1996, and, over time, became part of <a href="The_Open_Group" title="The Open Group">The Open Group</a>'s <a href="Common_Application_Environment" class="mw-redirect" title="Common Application Environment">Common Application Environment</a>.

</p><p>MS continued working with the original SQLC standard, retaining many of the advanced features that were removed from the CLI version. These included features like <a href="Cursor_(databases)#Scrollable_cursors" title="Cursor (databases)">scrollable cursors</a>, and <a href="Metadata" title="Metadata">metadata</a> information queries. The commands in the API were split into groups; the Core group was identical to the CLI, the Level 1 extensions were commands that would be easy to implement in drivers, while Level 2 commands contained the more advanced features like cursors. A proposed standard was released in December 1991, and industry input was gathered and worked into the system through 1992, resulting in yet another name change to <i>ODBC</i>.<sup id="cite_ref-FOOTNOTEGeiger1995203_9-0" class="reference"><a href="#cite_note-FOOTNOTEGeiger1995203-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup>

</p>

<p>During this time, Microsoft was in the midst of developing their <a href="Jet_Database_Engine" class="mw-redirect" title="Jet Database Engine">Jet database system</a>. Jet combined three primary subsystems; an <a href="ISAM" title="ISAM">ISAM</a>-based database engine (also named <i>Jet</i>, confusingly), a C-based interface allowing applications to access that data, and a selection of driver <a href="Dynamic-Link_Libraries" class="mw-redirect" title="Dynamic-Link Libraries">dynamic-link libraries</a> (DLL) that allowed the same C interface to redirect input and output to other ISAM-based databases, like <a href="Paradox_(database)" title="Paradox (database)">Paradox</a> and <a href="XBase" title="XBase">xBase</a>. Jet allowed using one set of calls to access common microcomputer databases in a fashion similar to Blueprint, by then renamed DataLens. However, Jet did not use SQL; like DataLens, the interface was in C and consisted of <a href="Data_structure" title="Data structure">data structures</a> and function calls.

</p><p>The SAG standardization efforts presented an opportunity for Microsoft to adapt their Jet system to the new CLI standard. This would not only make Windows a premier platform for CLI development, but also allow users to use SQL to access both Jet and other databases as well. What was missing was the SQL parser that could convert those calls from their text form into the C-interface used in Jet. To solve this, MS partnered with <a href="PageAhead_Software" class="mw-redirect" title="PageAhead Software">PageAhead Software</a> to use their existing query processor, SIMBA. SIMBA was used as a parser above Jet's C library, turning Jet into an SQL database. And because Jet could forward those C-based calls to other databases, this also allowed SIMBA to query other systems. Microsoft included drivers for Excel to turn its spreadsheet documents into SQL-accessible database tables.<sup id="cite_ref-simba_10-0" class="reference"><a href="#cite_note-simba-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Release_and_continued_development">Release and continued development</h3></div>

<p>ODBC 1.0 was released in September 1992.<sup id="cite_ref-11" class="reference"><a href="#cite_note-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup> At the time, there was little direct support for SQL databases (versus ISAM), and early drivers were noted for poor performance. Some of this was unavoidable due to the path that the calls took through the Jet-based stack; ODBC calls to SQL databases were first converted from <a href="Simba_Technologies" title="Simba Technologies">Simba Technologies</a>'s SQL dialect to Jet's internal C-based format, then passed to a driver for conversion back into SQL calls for the database. <a href="Digital_Equipment" class="mw-redirect" title="Digital Equipment">Digital Equipment</a> and <a href="Oracle_Corporation" title="Oracle Corporation">Oracle</a> both contracted <a href="Simba_Technologies" title="Simba Technologies">Simba Technologies</a> to develop drivers for their databases as well.<sup id="cite_ref-12" class="reference"><a href="#cite_note-12"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup>

</p><p>Circa 1993, OpenLink Software shipped one of the first independently developed third-party ODBC drivers, for the <a href="Progress_DBMS" class="mw-redirect" title="Progress DBMS">PROGRESS DBMS</a>,<sup id="cite_ref-13" class="reference"><a href="#cite_note-13"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup> and soon followed with their UDBC (a cross-platform API equivalent of ODBC and the SAG/CLI) SDK and associated drivers for <a href="Progress_Software" title="Progress Software">PROGRESS</a>, Sybase, Oracle, and other DBMS, for use on Unix-like OS (<a href="AIX" class="mw-redirect" title="AIX">AIX</a>, <a href="HP-UX" title="HP-UX">HP-UX</a>, <a href="Solaris_(operating_system)" class="mw-redirect" title="Solaris (operating system)">Solaris</a>, <a href="Linux" title="Linux">Linux</a>, etc.), <a href="OpenVMS" title="OpenVMS">VMS</a>, <a href="Windows_NT" title="Windows NT">Windows NT</a>, <a href="OS/2" title="OS/2">OS/2</a>, and other OS.<sup id="cite_ref-14" class="reference"><a href="#cite_note-14"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup>

</p><p>Meanwhile, the CLI standard effort dragged on, and it was not until March 1995 that the definitive version was finalized. By then, Microsoft had already granted Visigenic Software a <a href="Source_code" title="Source code">source code</a> license to develop ODBC on non-Windows platforms. Visigenic ported ODBC to the <a href="Classic_Mac_OS" title="Classic Mac OS">classic Mac OS</a>, and a wide variety of Unix platforms, where ODBC quickly became the de facto standard.<sup id="cite_ref-15" class="reference"><a href="#cite_note-15"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup> "Real" CLI is rare today. The two systems remain similar, and many applications can be ported from ODBC to CLI with few or no changes.<sup id="cite_ref-16" class="reference"><a href="#cite_note-16"><span class="cite-bracket">[</span>16<span class="cite-bracket">]</span></a></sup>

</p><p>Over time, database vendors took over the driver interfaces and provided direct links to their products. Skipping the intermediate conversions to and from Jet or similar wrappers often resulted in higher performance. However, by then Microsoft had changed focus to their <a href="OLE_DB" title="OLE DB">OLE DB</a><sup id="cite_ref-17" class="reference"><a href="#cite_note-17"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup> concept (recently reinstated <sup id="cite_ref-18" class="reference"><a href="#cite_note-18"><span class="cite-bracket">[</span>18<span class="cite-bracket">]</span></a></sup>), which provided direct access to a wider variety of data sources from <a href="Address_book" title="Address book">address books</a> to text files. Several new systems followed which further turned their attention from ODBC, including <a href="ActiveX_Data_Objects" title="ActiveX Data Objects">ActiveX Data Objects</a> (ADO) and <a href="ADO.net" class="mw-redirect" title="ADO.net">ADO.net</a>, which interacted more or less with ODBC over their lifetimes.

</p><p>As Microsoft turned its attention away from working directly on ODBC, the Unix field was increasingly embracing it. This was propelled by two changes within the market, the introduction of <a href="Graphical_user_interface" title="Graphical user interface">graphical user interfaces</a> (GUIs) like <a href="GNOME" title="GNOME">GNOME</a> that provided a need to access these sources in non-text form, and the emergence of <a href="Open_software" class="mw-redirect" title="Open software">open software</a> database systems like <a href="PostgreSQL" title="PostgreSQL">PostgreSQL</a> and <a href="MySQL" title="MySQL">MySQL</a>, initially under Unix. The later adoption of ODBC by Apple for using the standard Unix-side <a href="IODBC" title="IODBC">iODBC</a> package <a href="Mac_OS_X_10.2" class="mw-redirect" title="Mac OS X 10.2">Mac OS X 10.2</a> (Jaguar)<sup id="cite_ref-19" class="reference"><a href="#cite_note-19"><span class="cite-bracket">[</span>19<span class="cite-bracket">]</span></a></sup> (which OpenLink Software had been independently providing for Mac OS X 10.0 and even Mac OS 9 since 2001<sup id="cite_ref-20" class="reference"><a href="#cite_note-20"><span class="cite-bracket">[</span>20<span class="cite-bracket">]</span></a></sup>) further cemented ODBC as the standard for cross-platform data access.

</p><p><a href="Sun_Microsystems" title="Sun Microsystems">Sun Microsystems</a> used the ODBC system as the basis for their own open standard, <a href="Java_Database_Connectivity" title="Java Database Connectivity">Java Database Connectivity</a> (JDBC). In most ways, JDBC can be considered a version of ODBC for the programming language <a href="Java_(programming_language)" title="Java (programming language)">Java</a> instead of <a href="C_(programming_language)" title="C (programming language)">C</a>. JDBC-to-ODBC <i>bridges</i> allow Java-based programs to access data sources through ODBC drivers on platforms lacking a native JDBC driver, although these are now relatively rare. Inversely, ODBC-to-JDBC bridges allow C-based programs to access data sources through JDBC drivers on platforms or from databases lacking suitable ODBC drivers.

</p>

<div class="mw-heading mw-heading3"><h3 id="ODBC_today">ODBC today</h3></div>

<p>ODBC remains in wide use today, with drivers available for most platforms and most databases. It is not uncommon to find ODBC drivers for database engines that are meant to be embedded, like <a href="SQLite" title="SQLite">SQLite</a>, as a way to allow existing tools to act as front-ends to these engines for testing and debugging.<sup id="cite_ref-21" class="reference"><a href="#cite_note-21"><span class="cite-bracket">[</span>21<span class="cite-bracket">]</span></a></sup>

</p><p>In recent years, ODBC has also been adopted for connecting to cloud-based data sources and SaaS platforms such as <a rel="nofollow" class="external text" href="https://www.capterra.com/p/253037/ODBC-Driver-for-Salesforce/">Salesforce</a>, Google BigQuery, and Snowflake. Cross-platform driver availability (for Windows, macOS, and Linux) has enabled integration with modern analytics and business intelligence tools like Power BI, Tableau, and RStudio. This has extended ODBC’s relevance beyond traditional relational databases into cloud data warehousing and data science workflows.

</p>

<div class="mw-heading mw-heading3"><h3 id="Version_history">Version history</h3></div>

<div class="mw-heading mw-heading4"><h4 id="ODBC_specifications">ODBC specifications</h4></div>

<p>Source:<sup id="cite_ref-22" class="reference"><a href="#cite_note-22"><span class="cite-bracket">[</span>22<span class="cite-bracket">]</span></a></sup>

</p>

<ul><li>1.0: released in September 1992<sup id="cite_ref-23" class="reference"><a href="#cite_note-23"><span class="cite-bracket">[</span>23<span class="cite-bracket">]</span></a></sup></li>

<li>3.0: <abbr title="circa">c.</abbr> 1995, John Goodson of Intersolv and Frank Pellow and Paul Cotton of IBM provided significant input to ODBC 3.0<sup id="cite_ref-24" class="reference"><a href="#cite_note-24"><span class="cite-bracket">[</span>24<span class="cite-bracket">]</span></a></sup></li>

<li>3.8: <abbr title="circa">c.</abbr> 2009, with Windows 7<sup id="cite_ref-What's_New_in_ODBC_3.8_25-0" class="reference"><a href="#cite_note-What's_New_in_ODBC_3.8-25"><span class="cite-bracket">[</span>25<span class="cite-bracket">]</span></a></sup></li>

<li>4.0: Development announced June 2016<sup id="cite_ref-MSDA_blog_2016-06-07_26-0" class="reference"><a href="#cite_note-MSDA_blog_2016-06-07-26"><span class="cite-bracket">[</span>26<span class="cite-bracket">]</span></a></sup> with first implementation with SQL Server 2017 released Sep 2017 and additional desktop drivers late 2018 <a rel="nofollow" class="external text" href="https://github.com/Microsoft/ODBC-Specification">final spec on Github</a></li></ul>

<div class="mw-heading mw-heading4"><h4 id="Desktop_Database_Drivers">Desktop Database Drivers</h4></div>

<p>Source:<sup id="cite_ref-27" class="reference"><a href="#cite_note-27"><span class="cite-bracket">[</span>27<span class="cite-bracket">]</span></a></sup>

</p>

<ul><li>1.0 (1993–08): Used the SIMBA query processor produced by PageAhead Software.</li>

<li>3.0 (1995–10): Supports <a href="Windows_95" title="Windows 95">Windows 95</a> and Windows NT Workstation or NT Server 3.51. Only 32-bit drivers were included in this release.</li>

<li>3.5 (1996–10): Supports double-byte character set (DBCS), and accommodated the use of File data source names (DSNs). The Microsoft Access driver was released in an RISC version for use on Alpha platforms for Windows 95/98 and <a href="Windows_NT_3.51" title="Windows NT 3.51">Windows NT 3.51</a> and later operating systems.</li>

<li>4.0 (late 1998): Support Microsoft Jet Engine Unicode format along with compatibility for ANSI format of earlier versions.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Drivers_and_Managers">Drivers and Managers</h2></div>

<div class="mw-heading mw-heading3"><h3 id="Drivers">Drivers</h3></div>

<p>ODBC is based on the <a href="Device_driver" title="Device driver">device driver</a> model, where the driver encapsulates the logic needed to convert a standard set of commands and functions into the specific calls required by the underlying system. For instance, a <a href="Printer_driver" title="Printer driver">printer driver</a> presents a standard set of printing commands, the API, to applications using the printing system. Calls made to those APIs are converted by the driver into the format used by the actual hardware, say <a href="PostScript" title="PostScript">PostScript</a> or <a href="Printer_Command_Language" title="Printer Command Language">PCL</a>.

</p><p>In the case of ODBC, the drivers encapsulate many functions that can be broken down into several broad categories. One set of functions is primarily concerned with finding, connecting to and disconnecting from the DBMS that driver talks to. A second set is used to send SQL commands from the ODBC system to the DBMS, converting or interpreting any commands that are not supported internally. For instance, a DBMS that does not support <a href="Cursor_(databases)" title="Cursor (databases)">cursors</a> can emulate this functionality in the driver. Finally, another set of commands, mostly used internally, is used to convert data from the DBMS's internal formats to a set of standardized ODBC formats, which are based on the C language formats.

</p><p>An ODBC driver enables an ODBC-compliant application to use a <i>data source</i>, normally a DBMS. Some non-DBMS drivers exist, for such data sources as <a href="Comma-separated_values" title="Comma-separated values">CSV</a> files, by implementing a small DBMS inside the driver itself. ODBC drivers exist for most DBMSs, including <a href="Oracle_database" class="mw-redirect" title="Oracle database">Oracle</a>, <a href="PostgreSQL" title="PostgreSQL">PostgreSQL</a>, <a href="MySQL" title="MySQL">MySQL</a>, <a href="Microsoft_SQL_Server" title="Microsoft SQL Server">Microsoft SQL Server</a> (but not for the <a href="SQL_Server_Compact" title="SQL Server Compact">Compact aka CE edition</a>), <a href="Mimer_SQL" title="Mimer SQL">Mimer SQL</a>, <a href="Adaptive_Server_Enterprise" title="Adaptive Server Enterprise">Sybase ASE</a>, <a href="SAP_HANA" title="SAP HANA">SAP HANA</a><sup id="cite_ref-28" class="reference"><a href="#cite_note-28"><span class="cite-bracket">[</span>28<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-29" class="reference"><a href="#cite_note-29"><span class="cite-bracket">[</span>29<span class="cite-bracket">]</span></a></sup> and <a href="IBM_Db2" title="IBM Db2">IBM Db2</a>. Because different technologies have different capabilities, most ODBC drivers do not implement all functionality defined in the ODBC standard. Some drivers offer extra functionality not defined by the standard.

</p>

<div class="mw-heading mw-heading3"><h3 id="Driver_Manager">Driver Manager</h3></div>

<p>Device drivers are normally enumerated, set up and managed by a separate Manager layer, which may provide additional functionality. For instance, printing systems often include functionality to provide <a href="Spooling" title="Spooling">spooling</a> functionality on top of the drivers, providing print spooling for any supported printer.

</p><p>In ODBC the Driver Manager (DM) provides these features.<sup id="cite_ref-30" class="reference"><a href="#cite_note-30"><span class="cite-bracket">[</span>30<span class="cite-bracket">]</span></a></sup> The DM can enumerate the installed drivers and present this as a list, often in a GUI-based form.

</p><p>But more important to the operation of the ODBC system is the DM's concept of a <i>Data Source Name</i> (DSN). DSNs collect additional information needed to connect to a <i>specific</i> data source, versus the DBMS itself. For instance, the same <a href="MySQL" title="MySQL">MySQL</a> driver can be used to connect to any MySQL server, but the connection information to connect to a local private server is different from the information needed to connect to an internet-hosted public server. The DSN stores this information in a standardized format, and the DM provides this to the driver during connection requests. The DM also includes functionality to present a list of DSNs using human readable names, and to select them at run-time to connect to different resources.

</p><p>The DM also includes the ability to save partially complete DSN's, with code and logic to ask the user for any missing information at runtime. For instance, a DSN can be created without a required password. When an ODBC application attempts to connect to the DBMS using this DSN, the system will pause and ask the user to provide the password before continuing. This frees the application developer from having to create this sort of code, as well as having to know which questions to ask. All of this is included in the driver and the DSNs.

</p>

<div class="mw-heading mw-heading2"><h2 id="Bridging_configurations">Bridging configurations</h2></div>

<p>A <i>bridge</i> is a special kind of driver: a driver that uses another driver-based technology.

</p>

<div class="mw-heading mw-heading3"><h3 id="ODBC-to-JDBC_(ODBC-JDBC)_bridges">ODBC-to-JDBC (ODBC-JDBC) bridges</h3></div>

<p>An ODBC-JDBC bridge consists of an <i>ODBC</i> driver which uses the services of a <a href="JDBC_type_1_driver" class="mw-redirect" title="JDBC type 1 driver">JDBC driver</a> to connect to a database. This driver translates ODBC function-calls into JDBC method-calls. Programmers usually use such a bridge when they lack an ODBC driver for some database but have access to a JDBC driver. Examples: <a rel="nofollow" class="external text" href="https://uda.openlinksw.com/odbc-jdbc-st/">OpenLink ODBC-JDBC Bridge</a>, <a rel="nofollow" class="external text" href="https://www.progress.com/odbc/sequelink">SequeLink ODBC-JDBC Bridge</a>.

</p>

<div class="mw-heading mw-heading3"><h3 id="JDBC-to-ODBC_(JDBC-ODBC)_bridges">JDBC-to-ODBC (JDBC-ODBC) bridges</h3></div>

<p>A JDBC-ODBC bridge consists of a <a href="JDBC_driver" title="JDBC driver">JDBC driver</a> which employs an ODBC driver to connect to a target database. This driver translates JDBC <a href="Method_(computer_science)" class="mw-redirect" title="Method (computer science)">method</a> calls into ODBC function calls. Programmers usually use such a bridge when a given database lacks a JDBC driver, but is accessible through an ODBC driver. <a href="Sun_Microsystems" title="Sun Microsystems">Sun Microsystems</a> included one such bridge in the <a href="JVM" class="mw-redirect" title="JVM">JVM</a>, but viewed it as a stop-gap measure while few JDBC drivers existed (The built-in JDBC-ODBC bridge was dropped from the JVM in Java 8<sup id="cite_ref-31" class="reference"><a href="#cite_note-31"><span class="cite-bracket">[</span>31<span class="cite-bracket">]</span></a></sup>). Sun never intended its bridge for production environments, and generally recommended against its use. As of 2008 independent data-access vendors deliver JDBC-ODBC bridges which support current standards for both mechanisms, and which far outperform the JVM built-in. Examples: <a rel="nofollow" class="external text" href="https://uda.openlinksw.com/jdbc-odbc-st/">OpenLink JDBC-ODBC Bridge</a>, <a rel="nofollow" class="external text" href="https://www.progress.com/jdbc/sequelink">SequeLink JDBC-ODBC Bridge</a>, <a rel="nofollow" class="external text" href="https://zappysys.com/products/odbc-powerpack/odbc-jdbc-bridge-driver/">ZappySys JDBC-ODBC Bridge</a>.

</p>

<div class="mw-heading mw-heading3"><h3 id="OLE_DB-to-ODBC_bridges">OLE DB-to-ODBC bridges</h3></div>

<p>An OLE DB-ODBC bridge consists of an <a href="OLE_DB" title="OLE DB">OLE DB</a> Provider which uses the services of an ODBC driver to connect to a target database. This provider translates OLE DB <a href="Method_(computer_science)" class="mw-redirect" title="Method (computer science)">method</a> calls into ODBC function calls. Programmers usually use such a bridge when a given database lacks an OLE DB provider, but is accessible through an ODBC driver. Microsoft ships one, MSDASQL.DLL, as part of the <a href="Microsoft_Data_Access_Components" title="Microsoft Data Access Components">MDAC</a> system component bundle, together with other database drivers, to simplify development in COM-aware languages (e.g. <a href="Visual_Basic" title="Visual Basic">Visual Basic</a>). Third parties have also developed such, notably OpenLink Software whose 64-bit OLE DB Provider for ODBC Data Sources filled the gap when Microsoft initially deprecated this bridge for their 64-bit OS.<sup id="cite_ref-msdasql_32-0" class="reference"><a href="#cite_note-msdasql-32"><span class="cite-bracket">[</span>32<span class="cite-bracket">]</span></a></sup> (Microsoft later relented, and 64-bit Windows starting with <a href="Windows_Server_2008" title="Windows Server 2008">Windows Server 2008</a> and <a href="Windows_Vista_SP1" class="mw-redirect" title="Windows Vista SP1">Windows Vista SP1</a> have shipped with a 64-bit version of MSDASQL.) Examples: <a rel="nofollow" class="external text" href="https://uda.openlinksw.com/oledb-odbc-st/">OpenLink OLEDB-ODBC Bridge</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170327081146/https://uda.openlinksw.com/oledb-odbc-st/">Archived</a> 2017-03-27 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>, <a rel="nofollow" class="external text" href="https://www.progress.com/oledb/sequelink">SequeLink OLEDB-ODBC Bridge</a>.

</p>

<div class="mw-heading mw-heading3"><h3 id="ADO.NET-to-ODBC_bridges">ADO.NET-to-ODBC bridges</h3></div>

<p>An ADO.NET-ODBC bridge consists of an <a href="ADO.NET_data_provider" class="mw-redirect" title="ADO.NET data provider">ADO.NET Provider</a> which uses the services of an ODBC driver to connect to a target database. This provider translates ADO.NET <a href="Method_(computer_science)" class="mw-redirect" title="Method (computer science)">method</a> calls into ODBC function calls. Programmers usually use such a bridge when a given database lacks an ADO.NET provider, but is accessible through an ODBC driver. Microsoft ships one as part of the <a href="Microsoft_Data_Access_Components" title="Microsoft Data Access Components">MDAC</a> system component bundle, together with other database drivers, to simplify development in <a href="C_Sharp_(programming_language)" title="C Sharp (programming language)">C#</a>. Third parties have also developed such. Examples: <a rel="nofollow" class="external text" href="https://uda.openlinksw.com/dotnet-odbc-st/">OpenLink ADO.NET-ODBC Bridge</a>, <a rel="nofollow" class="external text" href="https://www.progress.com/net/sequelink">SequeLink ADO.NET-ODBC Bridge</a>.

</p>

<ul><li><a href="GNU_Data_Access" class="mw-redirect" title="GNU Data Access">GNU Data Access</a></li>

<li><a href="Java_Database_Connectivity" title="Java Database Connectivity">Java Database Connectivity</a> (JDBC)</li>

<li><a href="Windows_Open_Services_Architecture" title="Windows Open Services Architecture">Windows Open Services Architecture</a></li>

<li><a href="ODBC_Administrator" class="mw-redirect" title="ODBC Administrator">ODBC Administrator</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

<dl><dt>Bibliography</dt></dl>

/* start https://en.wikipedia.org/ */

.mw-parser-output .refbegin{margin-bottom:0.5em}.mw-parser-output .refbegin-hanging-indents>ul{margin-left:0}.mw-parser-output .refbegin-hanging-indents>ul>li{margin-left:0;padding-left:3.2em;text-indent:-3.2em}.mw-parser-output .refbegin-hanging-indents ul,.mw-parser-output .refbegin-hanging-indents ul li{list-style:none}@media(max-width:720px){.mw-parser-output .refbegin-hanging-indents>ul>li{padding-left:1.6em;text-indent:-1.6em}}.mw-parser-output .refbegin-columns{margin-top:0.3em}.mw-parser-output .refbegin-columns ul{margin-top:0}.mw-parser-output .refbegin-columns li{page-break-inside:avoid;break-inside:avoid-column}@media screen{.mw-parser-output .refbegin{font-size:90%}}

/* end https://en.wikipedia.org/ */

</style><div class="refbegin" style="">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFGeiger1995" class="citation book cs1">Geiger, Kyle (1995). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=G-ZQAAAAMAAJ"><i>Inside ODBC</i></a>. Microsoft Press. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781556158155</bdi>.</cite></li></ul>

</div>

<dl><dt>Citations</dt></dl>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1">^</a></b></span> <span class="reference-text">McGlinn, Evan (1988), <a rel="nofollow" class="external text" href="https://books.google.com/books?id=6D4EAAAAMBAJ">Blueprint Lets 1-2-3 Access Outside Data"</a>, <i>InfoWorld</i>, vol. 10, no. 14, 4 April 1988, pp. 1, 69</span>

</li>

<li id="cite_note-FOOTNOTEGeiger199565-2"><span class="mw-cite-backlink">^ <a href="#cite_ref-FOOTNOTEGeiger199565_2-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FOOTNOTEGeiger199565_2-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a href="#CITEREFGeiger1995">Geiger 1995</a>, p. 65.</span>

</li>

<li id="cite_note-FOOTNOTEGeiger199586-87-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEGeiger199586-87_3-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFGeiger1995">Geiger 1995</a>, p. 86-87.</span>

</li>

<li id="cite_note-FOOTNOTEGeiger199556-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEGeiger199556_4-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFGeiger1995">Geiger 1995</a>, p. 56.</span>

</li>

<li id="cite_note-FOOTNOTEGeiger1995106-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEGeiger1995106_5-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFGeiger1995">Geiger 1995</a>, p. 106.</span>

</li>

<li id="cite_note-FOOTNOTEGeiger1995165-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEGeiger1995165_6-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFGeiger1995">Geiger 1995</a>, p. 165.</span>

</li>

<li id="cite_note-FOOTNOTEGeiger1995186-187-7"><span class="mw-cite-backlink">^ <a href="#cite_ref-FOOTNOTEGeiger1995186-187_7-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FOOTNOTEGeiger1995186-187_7-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a href="#CITEREFGeiger1995">Geiger 1995</a>, p. 186-187.</span>

</li>

<li id="cite_note-ISO/IEC_9075-3-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-ISO/IEC_9075-3_8-0">^</a></b></span> <span class="reference-text">ISO/IEC 9075-3 – Information technology – Database languages – SQL – Part 3: Call-Level Interface (SQL/CLI)</span>

</li>

<li id="cite_note-FOOTNOTEGeiger1995203-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-FOOTNOTEGeiger1995203_9-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFGeiger1995">Geiger 1995</a>, p. 203.</span>

</li>

<li id="cite_note-simba-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-simba_10-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFHarindranathJože_Zupančič2001" class="citation book cs1">Harindranath, G; Jože Zupančič (2001). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=O8Loa-c0TyoC"><i>New perspectives on information systems development: theory, methods, and practice</i></a>. Springer. p. 451. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-306-47251-0</bdi><span class="reference-accessdate">. Retrieved <span class="nowrap">2010-07-28</span></span>. <q>The first ODBC drivers […] used the SIMBA query processor, which translated calls into the Microsoft Jet ISAM calls, and dispatched the calls to the appropriate ISAM driver to access the backend […]</q></cite></span>

</li>

<li id="cite_note-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-11">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.easysoft.com/developer/interfaces/odbc/linux.html#what_is_odbc">"Linux/UNIX ODBC – What is ODBC?"</a>.</cite></span>

</li>

<li id="cite_note-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-12">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.simba.com/simba-history.htm">"Our History"</a>, Simba Technologies</span>

</li>

<li id="cite_note-13"><span class="mw-cite-backlink"><b><a href="#cite_ref-13">^</a></b></span> <span class="reference-text"><cite id="CITEREFIdehen1994" class="citation web cs1">Idehen, Kingsley Uyi (October 1994). <a rel="nofollow" class="external text" href="https://groups.google.com/d/msg/comp.databases/ZDdiftnvkj4/AK0K2M0a0WoJ">"ODBC and progress V7.2d"</a>. <i>Usenet Newsgroup comp.databases</i><span class="reference-accessdate">. Retrieved <span class="nowrap">13 December</span> 2013</span>.</cite></span>

</li>

<li id="cite_note-14"><span class="mw-cite-backlink"><b><a href="#cite_ref-14">^</a></b></span> <span class="reference-text"><cite id="CITEREFIdehen1995" class="citation web cs1">Idehen, Kingsley Uyi (1995-07-18). <a rel="nofollow" class="external text" href="https://groups.google.com/d/msg/comp.databases.oracle/HSHhNjjBgf4/47PGF35h93AJ">"Need ODBC/Ingres driver for DEC OSF/1"</a>. <i>Usenet Newsgroup comp.databases.oracle</i><span class="reference-accessdate">. Retrieved <span class="nowrap">13 December</span> 2013</span>.</cite></span>

</li>

<li id="cite_note-15"><span class="mw-cite-backlink"><b><a href="#cite_ref-15">^</a></b></span> <span class="reference-text">Sippl, Roger (1996) <a rel="nofollow" class="external text" href="http://www.drdobbs.com/sql-access-groups-call-level-interface/184410032">"SQL Access Group's Call-Level Interface"</a>, Dr. Dobbs, 1 February 1996</span>

</li>

<li id="cite_note-16"><span class="mw-cite-backlink"><b><a href="#cite_ref-16">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://publib.boulder.ibm.com/infocenter/iisclzos/v9r5/index.jsp?topic=/com.ibm.swg.im.iis.fed.classic.clientsref.doc/topics/iiyfcodbcclisimdiff.html">"Similarities and differences between ODBC and CLI"</a>, InfoSphere Classic documentation, IBM, 26 September 2008</span>

</li>

<li id="cite_note-17"><span class="mw-cite-backlink"><b><a href="#cite_ref-17">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://hal2020.com/2011/09/25/ole-db-and-sql-server-history-end-game-and-some-microsoft-dirt/">"OLE DB and SQL Server: History, End-Game, and some Microsoft "dirt""</a>. 25 September 2011.</cite></span>

</li>

<li id="cite_note-18"><span class="mw-cite-backlink"><b><a href="#cite_ref-18">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://blogs.msdn.microsoft.com/sqlnativeclient/2017/10/06/announcing-the-new-release-of-ole-db-driver-for-sql-server/">"Announcing the new release of OLE DB Driver for SQL Server"</a>. 6 October 2017.</cite></span>

</li>

<li id="cite_note-19"><span class="mw-cite-backlink"><b><a href="#cite_ref-19">^</a></b></span> <span class="reference-text"><cite id="CITEREFAnderson2003" class="citation web cs1">Anderson, Andrew (2003-06-20). <a rel="nofollow" class="external text" href="http://oreilly.com/pub/a/mac/2003/06/20/odbc.html">"Open Database Connectivity in Jaguar"</a>. <i>O'Reilly MacDevCenter.com</i>. O'Reilly Media, Inc<span class="reference-accessdate">. Retrieved <span class="nowrap">13 December</span> 2013</span>.</cite></span>

</li>

<li id="cite_note-20"><span class="mw-cite-backlink"><b><a href="#cite_ref-20">^</a></b></span> <span class="reference-text"><cite id="CITEREFSellers2001" class="citation web cs1">Sellers, Dennis (2001-07-17). <a rel="nofollow" class="external text" href="http://www.macworld.com/article/1018465/odbc.html">"ODBC SDK update out for Mac OS Classic, Mac OS X"</a>. <i>MacWorld</i>. IDG Consumer & SMB<span class="reference-accessdate">. Retrieved <span class="nowrap">13 December</span> 2013</span>.</cite></span>

</li>

<li id="cite_note-21"><span class="mw-cite-backlink"><b><a href="#cite_ref-21">^</a></b></span> <span class="reference-text">Werner, Christian (2018) <a rel="nofollow" class="external text" href="http://www.ch-werner.de/sqliteodbc/">"SQLite ODBC Driver"</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20140626165719/http://www.ch-werner.de/sqliteodbc/">Archived</a> 2014-06-26 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>, 2018-02-24</span>

</li>

<li id="cite_note-22"><span class="mw-cite-backlink"><b><a href="#cite_ref-22">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.easysoft.com/developer/interfaces/odbc/linux.html#odbc_versions">"ODBC Versions"</a>. <i>Linux/UNIX ODBC</i>. Easysoft<span class="reference-accessdate">. Retrieved <span class="nowrap">2009-10-27</span></span>.</cite></span>

</li>

<li id="cite_note-23"><span class="mw-cite-backlink"><b><a href="#cite_ref-23">^</a></b></span> <span class="reference-text"><cite id="CITEREFAntal" class="citation web cs1">Antal, Tiberiu Alexandru. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20110722071727/http://www.east.utcluj.ro/mb/mep/antal/Articole/orajdbc_2004.pdf">"Access to an Oracle database using JDBC"</a> <span class="cs1-format">(PDF)</span>. Cluj-Napoca: Technical University of Cluj-Napoca. p. 2. Archived from <a rel="nofollow" class="external text" href="http://www.east.utcluj.ro/mb/mep/antal/Articole/orajdbc_2004.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2011-07-22<span class="reference-accessdate">. Retrieved <span class="nowrap">2009-10-27</span></span>. <q>ODBC 1.0 was released in September 1992</q></cite></span>

</li>

<li id="cite_note-24"><span class="mw-cite-backlink"><b><a href="#cite_ref-24">^</a></b></span> <span class="reference-text">Microsoft Corporation. Microsoft ODBC 3.0 Programmer's Reference and SDK Guide, Volume 1. Microsoft Press. February 1997. (<a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781572315167</bdi>)</span>

</li>

<li id="cite_note-What's_New_in_ODBC_3.8-25"><span class="mw-cite-backlink"><b><a href="#cite_ref-What's_New_in_ODBC_3.8_25-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://msdn.microsoft.com/en-us/library/ee388580%28VS.85%29.aspx">"What's New in ODBC 3.8"</a>. Microsoft<span class="reference-accessdate">. Retrieved <span class="nowrap">2010-01-13</span></span>. <q>Windows 7 includes an updated version of ODBC, ODBC 3.8.</q></cite></span>

</li>

<li id="cite_note-MSDA_blog_2016-06-07-26"><span class="mw-cite-backlink"><b><a href="#cite_ref-MSDA_blog_2016-06-07_26-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFRukmangathan2016" class="citation web cs1">Rukmangathan, Krishnakumar (2016-06-07). <a rel="nofollow" class="external text" href="https://blogs.msdn.microsoft.com/dataaccesstechnologies/2016/06/07/a-new-release-of-odbc-for-modern-data-stores/">"A new release of ODBC for Modern Data Stores"</a>. <i>Microsoft Data Access / SQL BI Technologies Blog</i>. Microsoft<span class="reference-accessdate">. Retrieved <span class="nowrap">2017-01-03</span></span>. <q>After more than 15 years since the last release, Microsoft is looking at updating the Open Data Base Connectivity (ODBC) specification.</q></cite></span>

</li>

<li id="cite_note-27"><span class="mw-cite-backlink"><b><a href="#cite_ref-27">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://learn.microsoft.com/en-us/sql/odbc/microsoft/history-of-the-desktop-database-drivers?view=sql-server-ver16">"History of the Desktop Database Drivers"</a>. 19 January 2017.</cite></span>

</li>

<li id="cite_note-28"><span class="mw-cite-backlink"><b><a href="#cite_ref-28">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://db-engines.com/en/system/SAP+HANA">"SAP HANA System Properties"</a>. <i>DB-Engines</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2016-03-28</span></span>.</cite></span>

</li>

<li id="cite_note-29"><span class="mw-cite-backlink"><b><a href="#cite_ref-29">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://help.sap.com/saphelp_hanaplatform/helpdata/en/66/a4169b84b2466892e1af9781049836/content.htm">"Connect to SAP HANA via ODBC - SAP HANA Developer Guide for SAP HANA Studio - SAP Library"</a>. <i>help.sap.com</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2016-03-28</span></span>.</cite></span>

</li>

<li id="cite_note-30"><span class="mw-cite-backlink"><b><a href="#cite_ref-30">^</a></b></span> <span class="reference-text"><cite id="CITEREFSybase" class="citation web cs1">Sybase. <a rel="nofollow" class="external text" href="http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.sdk_12.5.1.aseodbc/html/aseodbc/aseodbc5.htm">"Introduction to ODBC"</a>. <i>infocenter.sybase.com</i>. Sybase<span class="reference-accessdate">. Retrieved <span class="nowrap">8 October</span> 2011</span>.</cite></span>

</li>

<li id="cite_note-31"><span class="mw-cite-backlink"><b><a href="#cite_ref-31">^</a></b></span> <span class="reference-text"><cite id="31" class="citation web cs1"><a rel="nofollow" class="external text" href="https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc">"Java JDBC API"</a>. <i>docs.oracle.com</i><span class="reference-accessdate">. Retrieved <span class="nowrap">18 December</span> 2018</span>.</cite></span>

</li>

<li id="cite_note-msdasql-32"><span class="mw-cite-backlink"><b><a href="#cite_ref-msdasql_32-0">^</a></b></span> <span class="reference-text"><i>Microsoft</i>, "Data Access Technologies Road Map", Deprecated MDAC Components, <i>Microsoft</i> <a rel="nofollow" class="external text" href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdrefodbcprovspec.asp">"ADO Programmer's Guide" Appendix A: Providers, Microsoft OLE DB Provider for ODBC</a>, retrieved July 30, 2005. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20011005101137/http://msdn.microsoft.com/library/default.asp?url=%2Flibrary%2Fen-us%2Fado270%2Fhtm%2Fmdrefodbcprovspec.asp">Archived</a> 2001 October 5 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li><a rel="nofollow" class="external text" href="https://learn.microsoft.com/en-us/sql/odbc/reference/odbc-overview?view=sql-server-ver16">Microsoft ODBC Overview</a></li>

<li><a rel="nofollow" class="external text" href="https://www.ibm.com/docs/en/i/7.1?topic=administration-odbc">IBM i ODBC Administration</a></li>

<li><a rel="nofollow" class="external text" href="https://www.roth.net/perl/odbc/conf/sld002.htm">Presentation slides from www.roth.net</a></li>

<li><a rel="nofollow" class="external text" href="https://learn.microsoft.com/en-us/archive/blogs/data/data-access-api-of-the-day-part-i">Microsoft ODBC & Data Access APIs History Article</a>.</li>

<li>Github page: <a rel="nofollow" class="external text" href="https://github.com/microsoft/ODBC-Specification">Microsoft ODBC 4.0 Specification</a></li></ul>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="Microsoft_APIs_and_frameworks486" style="padding:3px"><table class="nowraplinks mw-collapsible mw-collapsed navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div id="Microsoft_APIs_and_frameworks486" style="font-size:114%;margin:0 4em"><a href="List_of_Microsoft_Windows_application_programming_interfaces_and_frameworks" title="List of Microsoft Windows application programming interfaces and frameworks">Microsoft APIs and frameworks</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em">Graphics and UI</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Desktop_Window_Manager" title="Desktop Window Manager">Desktop Window Manager</a></li>

<li><a href="Direct2D" title="Direct2D">Direct2D</a></li>

<li><a href="Direct3D" title="Direct3D">Direct3D</a></li>

<li><a href="D3DX" title="D3DX">D3D (extensions)</a></li>

<li><a href="Microsoft_Silverlight" title="Microsoft Silverlight">Silverlight</a></li>

<li><a href="Windows_UI_Library" title="Windows UI Library">WinUI</a></li>

<li><a href="Windows_Color_System" title="Windows Color System">Windows Color System</a></li>

<li><a href="Windows_Image_Acquisition" title="Windows Image Acquisition">Windows Image Acquisition</a></li>

<li><a href="Windows_Imaging_Component" title="Windows Imaging Component">Windows Imaging Component</a></li>

<li><a href="DirectX_Graphics_Infrastructure" title="DirectX Graphics Infrastructure">DirectX Graphics Infrastructure (DXGI)</a></li>

<li><a href="Windows_Advanced_Rasterization_Platform" title="Windows Advanced Rasterization Platform">Windows Advanced Rasterization Platform</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em">Audio</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="DirectMusic" title="DirectMusic">DirectMusic</a></li>

<li><a href="DirectSound" title="DirectSound">DirectSound</a></li>

<li><a href="Microsoft_Speech_API" title="Microsoft Speech API">Speech API</a></li>

<li><a href="XAudio2" title="XAudio2">XAudio2</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em">Multimedia</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="DirectX" title="DirectX">DirectX</a>

<ul><li><a href="DirectX_Media_Objects" class="mw-redirect" title="DirectX Media Objects">Media Objects</a></li>

<li><a href="DirectX_Video_Acceleration" title="DirectX Video Acceleration">Video Acceleration</a></li></ul></li>

<li><a href="Xinput" class="mw-redirect" title="Xinput">Xinput</a></li>

<li><a href="DirectInput" title="DirectInput">DirectInput</a></li>

<li><a href="DirectShow" title="DirectShow">DirectShow</a></li>

<li><a href="Managed_DirectX" title="Managed DirectX">Managed DirectX</a></li>

<li><a href="Media_Foundation" title="Media Foundation">Media Foundation</a></li>

<li><a href="Windows_Media" title="Windows Media">Windows Media</a></li>

<li><a href="Video_for_Windows" title="Video for Windows">Video for Windows</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em">Web</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Trident_(software)" title="Trident (software)">MSHTML</a></li>

<li><a href="JScript" title="JScript">JScript</a></li>

<li><a href="VBScript" title="VBScript">VBScript</a></li>

<li><a href="Microsoft_Gadgets" title="Microsoft Gadgets">SideBar Gadgets</a></li>

<li><a href="TypeScript" title="TypeScript">TypeScript</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em">Data access</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Microsoft_Data_Access_Components" title="Microsoft Data Access Components">Data Access Components (MDAC)</a>

<li><a href="Extensible_Storage_Engine" title="Extensible Storage Engine">Extensible Storage Engine</a></li>

<li><a href="Entity_Framework" title="Entity Framework">Entity Framework</a></li>

<li><a href="Microsoft_Sync_Framework" title="Microsoft Sync Framework">Sync Framework</a></li>

<li><a href="Access_Database_Engine" title="Access Database Engine">Access Database Engine</a></li>

<li><a href="MSXML" title="MSXML">MSXML</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em">Networking</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Winsock" title="Winsock">Winsock</a>

<li><a href="Windows_Vista_networking_technologies#Winsock_Kernel" title="Windows Vista networking technologies">Winsock Kernel</a></li>

<li><a href="Windows_Filtering_Platform" title="Windows Filtering Platform">Filtering Platform</a></li>

<li><a href="Windows_Rally" title="Windows Rally">Windows Rally</a></li>

<li><a href="DirectPlay" title="DirectPlay">DirectPlay</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em">Communication</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="MAPI" title="MAPI">Messaging API</a></li>

<li><a href="Telephony_Application_Programming_Interface" title="Telephony Application Programming Interface">Telephony API</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em">Administration and<br>management</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Win32_console" class="mw-redirect" title="Win32 console">Win32 console</a></li>

<li><a href="Windows_Script_Host" title="Windows Script Host">Windows Script Host</a></li>

<li><a href="Windows_Management_Instrumentation" title="Windows Management Instrumentation">WMI (extensions)</a></li>

<li><a href="PowerShell" title="PowerShell">PowerShell</a></li>

<li><a href="Windows_Task_Scheduler" title="Windows Task Scheduler">Task Scheduler</a></li>

<li><a href="Windows_Vista_I/O_technologies#Offline_Files" title="Windows Vista I/O technologies">Offline Files</a></li>

<li><a href="Shadow_Copy" title="Shadow Copy">Shadow Copy</a></li>

<li><a href="Windows_Installer" title="Windows Installer">Windows Installer</a></li>

<li><a href="Windows_Error_Reporting" title="Windows Error Reporting">Error Reporting</a></li>

<li><a href="Event_Viewer#Windows_Event_Log" title="Event Viewer">Event Log</a></li>

<li><a href="Common_Log_File_System" title="Common Log File System">Common Log File System</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em"><a href="Component-based_software_engineering" title="Component-based software engineering">Component model</a></th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="ActiveX" title="ActiveX">ActiveX</a></li>

<li><a href="Distributed_Component_Object_Model" title="Distributed Component Object Model">Distributed Component Object Model</a></li>

<li><a href=".NET_Framework" title=".NET Framework">.NET Framework</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em"><a href="Library_(computing)" title="Library (computing)">Libraries</a></th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Framework_Class_Library" title="Framework Class Library">Framework Class Library</a></li>

<li><a href="Microsoft_Foundation_Class_Library" title="Microsoft Foundation Class Library">Microsoft Foundation Classes (MFC)</a></li>

<li><a href="Active_Template_Library" title="Active Template Library">Active Template Library (ATL)</a></li>

<li><a href="Windows_Template_Library" title="Windows Template Library">Windows Template Library (WTL)</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em"><a href="Device_driver" title="Device driver">Device drivers</a></th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em">Security</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Microsoft_CryptoAPI" title="Microsoft CryptoAPI">Crypto API</a>

<ul><li><a href="CAPICOM" title="CAPICOM">CAPICOM</a></li></ul></li>

<li><a href="Windows_CardSpace" title="Windows CardSpace">Windows CardSpace</a></li>

<li><a href="Data_Protection_API" title="Data Protection API">Data Protection API</a></li>

<li><a href="Security_Support_Provider_Interface" title="Security Support Provider Interface">Security Support Provider Interface (SSPI)</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em"><a href=".NET_Framework" title=".NET Framework">.NET</a></th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href=".NET_Remoting" title=".NET Remoting">Remoting</a></li>

<li><a href="Microsoft_Silverlight" title="Microsoft Silverlight">Silverlight</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em"><a href="Software_Factory_(Microsoft_.NET)" class="mw-redirect" title="Software Factory (Microsoft .NET)">Software factories</a></th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Microsoft_Enterprise_Library" title="Microsoft Enterprise Library">Enterprise Library</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em"><a href="Inter-process_communication" title="Inter-process communication">IPC</a></th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Microsoft_RPC" title="Microsoft RPC">MSRPC</a></li>

<li><a href="Dynamic_Data_Exchange" title="Dynamic Data Exchange">Dynamic Data Exchange (DDE)</a></li>

<li><a href=".NET_Remoting" title=".NET Remoting">Remoting</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em">Accessibility</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Microsoft_Active_Accessibility" title="Microsoft Active Accessibility">Active Accessibility</a></li>

<li><a href="Microsoft_UI_Automation" title="Microsoft UI Automation">UI Automation</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;line-height:1.2em">Text and multilingual<br>support</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="DirectWrite" title="DirectWrite">DirectWrite</a></li>

<li><a href="Text_Services_Framework" title="Text Services Framework">Text Services Framework</a></li>

<li><a href="Text_Object_Model" title="Text Object Model">Text Object Model</a></li>

<li><a href="Input_method" title="Input method">Input method editor</a></li>

<li><a href="Language_Interface_Pack" title="Language Interface Pack">Language Interface Pack</a></li>

<li><a href="Multilingual_User_Interface" title="Multilingual User Interface">Multilingual User Interface</a></li>

<li><a href="Uniscribe" title="Uniscribe">Uniscribe</a></li></ul>

</div></td></tr></tbody></table></div>

<div class="navbox-styles"></div><div role="navigation" class="navbox authority-control" aria-label="Navbox390" style="padding:3px"><table class="nowraplinks hlist navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">Authority control databases: National </th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><span class="uid"><a rel="nofollow" class="external text" href="https://d-nb.info/gnd/4396455-2">Germany</a></span></li></ul></div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-07-28" href="https://en.wikipedia.org/wiki/?title=Open_Database_Connectivity&oldid=1302968124">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>